Open
Conversation
dev-rafiu
requested review from
adi-ray,
josephk-O,
lmcrean and
violaberg
as code owners
Owner
|
Opened this as a test for recent deployment branching feature, can't see any sign of it working. Will revert to draft but do open when you think it's ready for review @dev-rafiu thanks |
Owner
|
Looking at your branch I see latest changes aren't haven't been pulled? Would you mind doing this? Curious to test if we can deploy this from the PR as a means of speeding up review process @dev-rafiu Hope that makes sense |
This was referenced Oct 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please provide a clear and concise description of the changes made in this PR.
Screenshots / Screen Recordings
Please attach relevant screenshots or screen recordings that demonstrate UI/UX changes, Component behavior and /or Error messages (if applicable).
How to Test
Please provide step-by-step testing instructions. If any specific test data or test accounts are needed, mention them here.
README-developers.mdChecklist
Before submitting this PR, the following must be confirmed:
mainbranch and resolved any merge conflictscd frontend && npm run buildto confirm no type or build errorsnpm run lint) and fixed warnings/errorsIssue Links
Mention Related Issues (e.g. Fixes #123, Closes #456, as per closing keywords guidance). When updating you can also use the PR sidebar on the right-hand link via the
developmenttab -- this will automatically close the issue when the PR gets mergedAdditional Notes
(Any additional information for reviewers, like known bugs, workarounds, or future improvements.)